Otto Kekäläinen [Fri, 12 Dec 2025 08:53:33 +0000 (08:53 +0000)]
MDEV-37098 Fix Spider test failures in network-less environments
When running tests in environments without a network interface (such as
containers with `--network=none`), Spider could not retrieve a hardware
address to generate a node ID. This triggered a warning in the server
log, causing MTR to fail the test due to unexpected output:
[Warning] mariadbd: Can't get hardware address with error 2
Fix this by logging Spider hardware address errors to server log only.
This ensures the message is recorded in the server log for debugging but
does not pollute the client output.
It is questionable if this is a problem at all anyway, as when
`my_gethwaddr` fails, the code zeroes out the address buffer, resulting
in a `spider_unique_id` formatted like `-000000000000-PID-`, which is
valid.
When the test is starting up the server with innodb_force_recovery=1,
there will be messages about the LSN being in the future. The current
LSN is expected to be 12338 plus any number of FILE_CHECKPOINT records
(16 bytes each). We have observed anything up to 12402=12338+16*4 in
our CI systems. To be on the safe side, let us allow up to ten records.
Aquila Macedo [Sat, 8 Nov 2025 00:09:05 +0000 (21:09 -0300)]
[PATCH] MDEV-38046 Make func_regexp_pcre tolerant to PCRE2 offset change
PCRE2 10.47 reports the invalid escape in 'A\q' at offset 3 instead of 2.
Update the expected result and add a --replace_regex in the test so the
suite passes with both older and newer PCRE2 versions.
Forwarded: https://jira.mariadb.org/browse/MDEV-38046
(accepted upstream, will be in MariaDB 11.8.6+)
Otto Kekäläinen [Fri, 8 Aug 2025 04:30:51 +0000 (21:30 -0700)]
Suppress native AIO warning introduced in 10.8.3
Upstream a87bb96 introduced a new warning, visible at least on all ppc64el and
s390x builds which makes the post-build mariadb-test-test fail:
[Warning] InnoDB: native AIO failed: falling back to
innodb_use_native_aio=OFF
The case of this is the ci environment only where there is insufficent
fs.aio-max-nr configured. A such we are adding a suppression to the
mtr only. The warning is valuable for users. Upstream MDEV-37411 has
added a io_setup as a warning, which will fail in the CI environment,
so we're pre-emptively suppressing this warning too.
Unlike upstream MariaDB, in Debian we removed libaio in for Linux on
MariaDB 10.6+ in 612630c6 and completely in 1d648d6f. This was re-added
by upstream added a system variable innodb_linux_aio to control, and
also provided automated fallback. As such we're readding it back too.
With liburing still seccomp filterer in container environments having
a libaio fallback is more valuable than the threads implementation of
last resort.
Edited & Updated: Daniel Black <daniel@mariabdb.org>
Upstream rejected this with the conclusion, is that it will start working in
Debian/Salsa/Ubuntu/Launchpad once the Linux kernel is new enough to handle the
I/O calls and fallbacks properly, or once the CI system increases the value of
/proc/sys/fs/aio-max-nr to 1 million or so, to allow multiple parallel MariaDB
servers (as started by mariadb-test-run) each have enough quota for native AIO
to work.
Gbp-Pq: Name MDEV-37411-suppress-new-warning-about-native-aio.patch
Otto Kekalainen [Sun, 30 Jun 2024 15:18:06 +0000 (15:18 +0000)]
Disable the 'mysql*' command deprecation warning
Many command-line tools expect the commands they run to return without
any output in stderr or having error codes. The fact that now in MariaDB
11.4 all 'mysql*' commands emit a deprecation warning causes a lot of
scripts to fail, such as the /etc/init.d/mariadb itself and many dependent
programs as witnessed via Debian autopkgtests. See examples below.
Otto Kekalainen [Sun, 10 Mar 2024 16:56:13 +0000 (16:56 +0000)]
Show banner in server and client startup to drive community engagement
Suggest to users that they can support MariaDB development by simply giving a
star on GitHub. This patch experiments with how well such a banner works, and
may later change the contents to drive some other kind of engagement.
Client output:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 11.8.1-MariaDB-5 from Debian -- Please help get to 10k stars at https://github.com/MariaDB/Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
Server output:
[Note] Please help get to 10k stars at https://github.com/MariaDB/Server
Server output if built in git directory:
[Note] Starting MariaDB 11.8.1-MariaDB-5 from Debian source revision 1a9c3debfd6b1b16af4e501d3530b866b85c38a8 server_uid eNAjF8/wvUNM09/mSmh+k3a5o5w= as process 1359
Logs will also show as server output:
mysqld: Version: '11.8.1-MariaDB-5 from Debian' socket: '/run/mysqld/mysqld.sock' port: 3306 -- Please help get to 10k stars at https://github.com/MariaDB/Server
Upstream will never accept this patch,
see https://github.com/MariaDB/server/pull/1718
Origin: https://patch-diff.githubusercontent.com/raw/MariaDB/server/pull/1718.patch
Forwarded: https://github.com/MariaDB/server/pull/1718 (rejected, will never be merged)
Otto Kekäläinen [Tue, 13 Jan 2026 19:03:57 +0000 (19:03 +0000)]
mariadb (1:11.8.5-4) unstable; urgency=medium
[ Otto Kekäläinen ]
* Add tentative upstream patch to fix amd64v3 build issues (MDEV-38398)
* Drop redundant `Priority: optional`
* Update Debian copyright for 2026
* Bump Debian Policy version
[ Aquila Macedo ]
* Drop obsolete library-not-linked-against-libc overrides
* Ship upstream sysusers.d mariadb.conf in mariadb-server (Closes: #1028271)
* Add patch sysusers-lock-mysql-account.patch
* Create mysql via sysusers in postinst, drop preinst adduser handling
* Drop adduser pre-depends, depend on systemd-sysusers provider
* Clarify NIS/YP debconf note for sysusers mysql account creation
* Update all translations to match updated template
projects / mariadb.git / log